Version Packages#1171
Merged
Merged
Conversation
6a38709 to
0207c30
Compare
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | b2ca44e | Jun 29 2026, 12:12 AM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | b2ca44e | Commit Preview URL Branch Preview URL |
Jun 29 2026, 12:10 AM |
0207c30 to
1edfd8e
Compare
Contributor
Cloudflare previewTorn down — the PR is closed. |
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/codemode-core
@executor-js/runtime-quickjs
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
executor
commit: |
2ac9512 to
ceec15f
Compare
ceec15f to
b2ca44e
Compare
RhysSullivan
added a commit
that referenced
this pull request
Jun 29, 2026
* Revert "Version Packages (#1171)" This reverts commit a7d4603. * Release changesets as patch to avoid fixed-group major escalation The update-available-notifications changeset marked @executor-js/api and @executor-js/react as minor. With the changesets fixed group, any minor in the release escalates the whole fixed group to a major bump, which is what produced the unintended 2.0.0. Setting every entry to patch keeps the re-release a 1.5.23 patch.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@executor-js/cli@0.2.29
Patch Changes
@executor-js/config@2.0.0
Patch Changes
@executor-js/execution@2.0.0
Patch Changes
@executor-js/vite-plugin@0.0.40
Patch Changes
@executor-js/runtime-quickjs@2.0.0
Patch Changes
@executor-js/plugin-desktop-settings@2.0.0
Patch Changes
@executor-js/plugin-example@2.0.0
Patch Changes
@executor-js/plugin-file-secrets@2.0.0
Patch Changes
@executor-js/plugin-google@2.0.0
Patch Changes
fd29abe,b6c8968]:@executor-js/plugin-graphql@2.0.0
Patch Changes
#1173
cc94666Thanks @RhysSullivan! - Fix the GraphQL plugin generating invalid operations against large schemas, and make field selection caller-controlled instead of a baked-in guess.Previously each tool froze a recursive, depth- and count-bounded selection at sync time. Against a rich schema (GitLab) this produced invalid GraphQL (composite fields with no sub-selection, nested fields missing required arguments) so every call over a rich return type failed, and the arbitrary bound silently truncated which fields came back.
Generated tools now default to selecting only scalar/enum leaf fields of the return type (always valid, always within a server's query-complexity budget), and expose an optional
selectinput carrying a GraphQL selection set so a caller can request nested or list data per call (including supplying nested required arguments). Fixes #1146.Updated dependencies [
fd29abe,b6c8968]:@executor-js/plugin-keychain@2.0.0
Patch Changes
@executor-js/plugin-mcp@2.0.0
Patch Changes
fd29abe,b6c8968]:@executor-js/plugin-microsoft@2.0.0
Patch Changes
fd29abe,b6c8968]:@executor-js/plugin-onepassword@2.0.0
Patch Changes
fd29abe,b6c8968]:@executor-js/plugin-openapi@2.0.0
Patch Changes
fd29abe,b6c8968]:@executor-js/plugin-toolkits@2.0.0
Patch Changes
fd29abe,b6c8968]:@executor-js/sdk@2.0.0
@executor-js/codemode-core@2.0.0
executor@2.0.0
Minor Changes
b6c8968Thanks @RhysSullivan! - Notify when a newer Executor is published. The CLI now prints an "update available" line under its ready banner, and the web shell's sidebar update card works for real (a new/v1/app/npm/dist-tagsendpoint backs it). In the desktop app the card shows a native "Restart to update" action wired to the in-app updater instead of the npm command. The check is best-effort and offline-safe, and can be disabled withEXECUTOR_DISABLE_UPDATE_CHECK.Patch Changes
#1170
0de0106Thanks @RhysSullivan! - Add a test seam to skip the first-run "keep Executor running in the background?" consent dialog under automation, matching the existingconfirmResetStateseam. SetEXECUTOR_TEST_AUTO_CONFIRM_BACKGROUND_SERVICE=1to keep the background service or any other value to decline. When the variable is unset the dialog is shown exactly as before. Native dialogs cannot be answered from CDP or Playwright, so a packaged first-run boot under automation previously blocked at this prompt with no way to proceed.#1169
94647f1Thanks @RhysSullivan! - Fix the desktop app failing to start its local server when the generated auth token begins with a dash. The token israndomBytes(32).toString("base64url"), which can start with "-", and the packaged app passed it to the bundled CLI as a separate argument (--auth-token, then the token). The CLI then read the leading-dash token as an unknown flag, printed its help, and exited, so the desktop showed a fatal "local Executor server crashed during startup" dialog. This was persistent (the token is saved) and cross-platform, affecting roughly 1 in 64 fresh installs. The token is now passed in the combined--auth-token=<value>form so a leading dash is treated as the value.Updated dependencies [
fd29abe,b6c8968]:@executor-js/desktop@2.0.0
Minor Changes
b6c8968Thanks @RhysSullivan! - Notify when a newer Executor is published. The CLI now prints an "update available" line under its ready banner, and the web shell's sidebar update card works for real (a new/v1/app/npm/dist-tagsendpoint backs it). In the desktop app the card shows a native "Restart to update" action wired to the in-app updater instead of the npm command. The check is best-effort and offline-safe, and can be disabled withEXECUTOR_DISABLE_UPDATE_CHECK.@executor-js/api@1.5.0
Minor Changes
b6c8968Thanks @RhysSullivan! - Notify when a newer Executor is published. The CLI now prints an "update available" line under its ready banner, and the web shell's sidebar update card works for real (a new/v1/app/npm/dist-tagsendpoint backs it). In the desktop app the card shows a native "Restart to update" action wired to the in-app updater instead of the npm command. The check is best-effort and offline-safe, and can be disabled withEXECUTOR_DISABLE_UPDATE_CHECK.Patch Changes
#1197
fd29abeThanks @RhysSullivan! - Fix OAuth "Mismatching redirect URI" for org-scoped client-id metadata documentsOrg-scoped client-id metadata documents registered their callback as
redirect_uriwith anexecutor_orgquery param, but the client always sendsthe bare callback and the org is carried in the OAuth
state. Providers thatcompare
redirect_urias an exact string (such as PostHog) rejected theauthorize request. Org targets now keep their distinct
client_idURL butregister the same bare callback
redirect_urias every other target.Updated dependencies []:
@executor-js/react@1.5.0
Minor Changes
b6c8968Thanks @RhysSullivan! - Notify when a newer Executor is published. The CLI now prints an "update available" line under its ready banner, and the web shell's sidebar update card works for real (a new/v1/app/npm/dist-tagsendpoint backs it). In the desktop app the card shows a native "Restart to update" action wired to the in-app updater instead of the npm command. The check is best-effort and offline-safe, and can be disabled withEXECUTOR_DISABLE_UPDATE_CHECK.Patch Changes
fd29abe,b6c8968]:@executor-js/cloud@1.4.41
Patch Changes
fd29abe,cc94666,b6c8968]:@executor-js/host-selfhost@0.0.22
Patch Changes
fd29abe,cc94666,b6c8968]:@executor-js/e2e@0.0.20
Patch Changes
fd29abe,cc94666,b6c8968]:@executor-js/example-all-plugins@0.0.41
Patch Changes
cc94666]:@executor-js/example-docs-sdk-quickstart@0.0.26
Patch Changes
@executor-js/cloudflare@0.0.22
Patch Changes
fd29abe,b6c8968]:@executor-js/plugin-encrypted-secrets@0.0.22
Patch Changes